Systems and methods for generating and updating dynamic digital tickets within a digital board

ABSTRACT

A communication application may include a request-response mechanism, which may enable real-time interaction between multiple users executing multiple tasks at multiple locations. Using the communication application, a first user may generate a digital ticket for the tasks, which may be shared with a second user. A response associated with the digital ticket by the second user may occur in a particular structured format within the communication application. The response may include location information of the second user and status of machines executing the tasks. The communication application may bring every user action and response data associated with the tasks into one unique digital board associated with the communication application. The digital board may create and implement a collaborative network and successfully orchestrate value-exchanging interactions among the users in the data sharing ecosystem.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/645,082, filed on Mar. 19, 2018, which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

This application relates generally to the field of dynamic digitaltickets, and more specifically to methods, systems, and computer programproducts for generating and updating dynamic digital tickets withindigital boards.

BACKGROUND

Conventional mobile communication tools (e.g., mobile applications) areinadequate for data capture and data sharing. These tools merely captureand store communications between the different entities. For example,messaging platforms such as WhatsApp or Facebook Messenger supportgroups and group conversations. The group conversations are limited totext, audio, video, or icons. There is no mechanism or tool forstructured data capture and sharing of the captured data.

In addition to the inadequacy of the conventional mobile communicationtools for data capture and sharing, there is no mechanism for digitalrecordkeeping based on the communications within the mobilecommunication tools. All the conventional communication tools provide isan archive for the messages that are passed around. Although thearchived message may be text searched, there are no data structures fordigital recordkeeping based upon captured and shared data.

A farm typically has multiple and parallel farming operationsdistributed across various locations and performed by a combination ofpeople and machinery. For example, ploughing and sowing operations maybe in a parcel of land and may involve a tractor and a tractor operator.Pasturing operations may involve transporting cattle from corral topasture and not involve any machinery. The technical challenge thereforeis to track, share, and digitally record the statuses and/or any otherinformation of these varied operations. Furthermore, as farming involvesvarious on-field (e.g., outdoor operations), the digital tools fortracking, sharing, and digital recordkeeping have to be supported bymobile devices and/or any other type of embedded devices.

However, as described above, the conventional mobile applications do notadequately address the aforementioned technical challenge.

SUMMARY

What is therefore needed are digital tracking, sharing, andrecordkeeping systems and methods for farming operations or any othertype of operations. What is further needed are the systems and methodsthat can be hosted by and performed by mobile devices such assmartphones.

Embodiments disclosed herein attempt to solve the aforementionedtechnical problems and may provide other benefits as well. Anillustrative communication system may include an arrangement of hardwarecomponents and software algorithms, which may be configured to generateand update dynamic digital tickets within a digital board. The digitalboard is presented on a communication application, which is beingexecuted on computing devices of the participants. The digital ticketsmay be associated with the one or more tasks, which have to be performedby one or more participants at the one or more locations using one ormore machines. The digital tickets may be updated based on real-timedata associated with the execution of the one or more tasks by the oneor more participants. The real-time data may include location dataassociated with the participants and status of the one or more machinesbeing used to execute the one or more tasks. Using the real-time sharingof the data between the computing devices of the participants operatingat different locations via the dynamic updating of the digital tickets,the communication system may enable efficient and structuredinteractions associated with the one or more tasks on the digital boardbetween the participants.

In one embodiment, a computer-implemented method may include generating,by a first instance of an application in a first computer, a digitalboard associated with a farm project within a workspace associated witha first type of farm operation; generating, by the first instance of theapplication in the first computer, a digital ticket within the digitalboard, the digital ticket configured for a farm task associated with thefarm project, and the digital ticket including a data templateconfigured to receive data records associated with the farm task;transmitting, by the first instance of the application in the firstcomputer, the digital ticket to a second instance of the application ina second computer; receiving, by a second instance of the application ina second computer, the digital ticket transmitted by the first instanceof the application in the first computer; in response to the secondinstance of the application in the second computer receiving anindication to activate the digital ticket; continuously tracking, by thesecond instance of the application in the second computer, thegeolocation of the second computer; continuously retrieving, by thesecond instance of the application in the second computer, dispensingdata through an application programming interface of a farm machineryassociated with the farm task; continuously updating, by the secondinstance of the application in the second computer, the digital ticketbased on the continuously tracked geolocation and continuously retrieveddispensing data; determining, by the second instance of the applicationin the second computer, that the farm task is complete based upon thecontinuous updates to the digital ticket; and transmitting, by thesecond instance of the application in the second computer to the firstinstance of the application in the first computer, a final updateddigital ticket and a notification that the farm task is complete.

In another embodiment, a system may include a first computer having afirst application of an application, wherein the first instance of theapplication in the first computer is configured to: generate a digitalboard associated with a farm project within a workspace associated witha first type of farm operation; generate a digital ticket within thedigital board, the digital ticket configured for a farm task associatedwith the farm project, and the digital ticket including a data templateconfigured to receive data records associated with the farm task;transmit the digital ticket to a second instance of the application in asecond computer, wherein the second instance of the application in thesecond computer is configured to: receive a second instance of theapplication in a second computer, the digital ticket transmitted by thefirst instance of the application in the first computer; in response tothe second instance of the application in the second computer receivingan indication to activate the digital ticket; continuously track thegeolocation of the second computer; continuously retrieve dispensingdata through an application programming interface of a farm machineryassociated with the farm task; continuously update the digital ticketbased on the continuously tracked geolocation and continuously retrieveddispensing data; determine that the farm task is complete based upon thecontinuous updates to the digital ticket; and transmit to the firstinstance of the application in the first computer, a final updateddigital ticket and a notification that the farm task is complete.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings constitute a part of this specification andillustrate embodiments of the subject matter disclosed herein.

FIG. 1A shows a communication system for enabling interaction betweenusers executing one or more tasks at one or more locations, according toan embodiment.

FIG. 1B shows a board containing multiple tickets, according to anembodiment.

FIG. 2A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 2B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 2C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 3A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 3B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 4A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 4B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 5 shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 6A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 6B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 7A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 7B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 7C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 8A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 8B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 8C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 8D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 9A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 9B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 9C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 10A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 10B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 10C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 11A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 11B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 11C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 11D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 12A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 12B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 12C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 12D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 12E shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 13A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 13B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 13C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 14A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 14B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 15A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 15B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 15C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 16A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 16B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 17A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 17B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 18A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 18B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 18C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 19A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 19B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 19C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 19D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 20A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 20B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 20C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 21A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 21B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 22A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 22B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 22C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 22D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 23A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 23B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 23C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 23D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 24A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 24B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 24C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 25A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 25B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 25C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 26A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 26B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 26C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 27A shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 27B shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 27C shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 27D shows a graphical user interface showing a webpage of acommunication application executing on a computing device, according toan embodiment.

FIG. 28 shows a flowchart for enabling interaction between usersexecuting one or more tasks at one or more locations, according to anembodiment.

FIG. 29 shows a graphical user interface showing a registration processof a communication application executing on a computing device,according to an embodiment.

FIG. 30 shows a graphical user interface showing a registration processof a communication application executing on a computing device,according to an embodiment.

FIG. 31 shows a graphical user interface showing a registration processof a communication application executing on a computing device,according to an embodiment.

FIG. 32 shows a graphical user interface showing digital boards andtasks on a communication application executing on a computing device,according to an embodiment.

FIG. 33 shows a graphical user interface showing a list of digitalboards on a communication application executing on a computing device,according to an embodiment.

FIG. 34 shows a graphical user interface showing a list of tasks on acommunication application executing on a computing device, according toan embodiment.

FIG. 35 shows a graphical user interface showing a process for enteringa task on a digital board in a communication application executing on acomputing device, according to an embodiment.

FIG. 36 shows a graphical user interface showing a process for selectinga digital board in a communication application executing on a computingdevice, according to an embodiment.

FIG. 37A shows a graphical user interface showing a process for editinga digital board in a communication application executing on a computingdevice, according to an embodiment.

FIG. 37B shows a graphical user interface showing a process for adding aname of a digital board in a communication application executing on acomputing device, according to an embodiment.

FIG. 37C shows a graphical user interface showing a process for addingparticipants in a digital board in a communication application executingon a computing device, according to an embodiment.

FIG. 37D shows a graphical user interface showing a process for addingdate and time in a digital board in a communication applicationexecuting on a computing device, according to an embodiment.

FIG. 37E shows a graphical user interface showing a process for addingactions on a digital board in a communication application executing on acomputing device, according to an embodiment.

FIG. 37F shows a graphical user interface showing a summary of a digitalboard in a communication application executing on a computing device,according to an embodiment.

FIG. 38A shows a graphical user interface showing a digital board in acommunication application executing on a computing device, according toan embodiment.

FIG. 38B shows a graphical user interface showing a history of a digitalboard in a communication application executing on a computing device,according to an embodiment.

DETAILED DESCRIPTION

Embodiments disclosed herein describe systems and methods for generatingand updating dynamic digital tickets within digital boards. A digitalboard may be associated with a farm project and the dynamic digitaltickets may be configured for a farm task within the farm project. Thedigital boards and the dynamic digital tickets may be implemented withinan application such as a mobile phone application (also referred to ascommunication application). Once a dynamic digital ticket isinstantiated within a corresponding digital board, the associatedparticipants may update the dynamic digital ticket. Furthermore, themobile phone application may automatically update the dynamic digitalticket based upon data such as geolocation data or data retrieved fromapplication programming interfaces (APIs) of other devices. The mobilephone application (or any other computing system) may use the updates tothe dynamic digital ticket for digital recordkeeping.

The digital board may be associated with a set of parameters. The set ofparameters may include title, participants, time, and action. Thecommunication application may be configured to bring every user actioninto one unique digital board. The user actions may include, but notlimited to, measurement of information, communication between the users,task planning, and execution control associated with data, such as, farmoperation data.

The digital board may be configured to create and implement acollaborative communication network. The digital board may orchestratevalue-exchanging interactions among the users in the data sharingecosystems using information about the various users. The data sharingecosystems may be multifarious, diversified, and comprehensive, inresponse to rapidly evolving farming markets, and requirements of theusers or other interested parties. The other interested parties may notnecessarily be the users of the communication application. The otherinterested parties may cause a different software program to beintegrated with the communication application, and thereby allowingcooperation of the communication application with the different softwareprogram.

Using the digital board, the users may invite and connect with otherusers, and share content, data, and various tasks within the digitalboard with the other users. During the sharing and communicationprocess, the digital board may work as a container of all the farm datashared between the users. The users may communicate, via a messagingchat application, in each digital board. During the communicationsession, communication data may be generated. All the communication datamay be stored for easy and convenient ‘anywhere, anytime’ access by theusers via the communication application.

The users may execute instructions to create the dynamic digital tickets(also referred to as digital tickets) within the digital board, andassign specific tasks to other users along with selected time ranges andinstructions. The users may input the data on the digital board, viaautomated software-generated input, where the users may connect topre-defined data providers (for example, plug-and-play infrastructurevia built-in APIs). The users may customize and personalize the form andthe view of the digital boards, which may result in tailoredpresentation of the digital ticket on the digital board.

The communication application may solve ‘in-the-farm’ problems, such as,user management, farming tasks planning and control, farming activitiesplanning and control, farming record-keeping, and real-timecommunication between the users. The communication application may savetime for the users for management of the farm data, and get things donein the farm by eliminating the use of paper and inefficient ways ofcommunication among the users of the farm. The communication applicationmay provide a platform for an easy input of data for the users, via adigital board framework, which may include subject matter informationand user's information.

A computing device (e.g., a mobile phone) may execute a communicationapplication, which may facilitate interaction between two or more usersvia a digital board associated with the communication application.During the interaction, transfer of electronic data messages may occurbetween the computing devices of the users. A user may command thecommunication application to transmit a task or share farm data withother users, via a data processing system, which may host the digitalboard. The data processing system may be associated with various socialmedia processing systems, which may provide instructions to the dataprocessing system to transmit task from the digital board associatedwith a first user to the same digital board associated with a seconduser.

Although the communication application described herein as taking a formof a messaging application on the computing devices, it should beappreciated that some embodiments are not limited to such a form factor.For instance, in some cases, the users may access the data processingsystem via a website. The data processing system may include a webserverin communication with an application server, which may be configured toperform various processes and tasks described herein. The user mayaccess the data processing system through a native application (e.g.,the communication application) installed on a local computing device ofthe user, which was downloaded from a server of the data processingsystem. Additionally or alternatively, the user may access the dataprocessing system through an Internet browser application through whichthe user may provide various process instructions to the webserver ofthe data processing system. Other embodiments of the communicationapplication may include a messaging application, executed by thecomputing device, through which the user interfaces with the dataprocessing system, via a chat messaging interface, on the computingdevice of the user. The data processing system may then perform varioustasks and processes described herein, based upon the chat-based (e.g.,SMS, iMessage®) instructions received from the computing device of theuser.

When the user having an account associated with the communicationapplication uses the computing device to execute the communicationapplication to share information with other users on the digital board,the user may be required to enter login details to access thecommunication application on the computing device. Upon the entry oflogin information by the user, the data processing system that runs(e.g., executes and controls the functional behavior of) thecommunication application may execute a layer of security protocols toverify an identity of the user. For instance, upon entry of the logininformation in the communication application, the user may receive acode on the computing device of the user. The user may enter the codeinto a graphical user interface associated with webpages of thecommunication application on the computing device to verify that theaccount being accessed by the user belongs to the user. When the codeentered by the user is correct, the data processing system may allow theuser to access the communication application on the computing device, toaccess digital board, create digital tickets, and share and view thedata corresponding to the digital ticket on the digital board associatedwith the communication application.

A communication system (e.g., a system that manages communicationapplication, the digital board, and the digital tickets) may beconfigured for aggregating the data associated with the farm operationfrom different devices on a real-time basis. For example, thecommunication system may aggregate the operation data and the locationdata from a first device of a first farm user assigned to managelivestock and from a second device of a second farm user assigned tocrop management. The communication system may analyze aggregated data togenerate various results, such as, characteristics of the farm harvest,volume of the farm harvest, information about efficiency of farming, andfarm production. The results may include various statistics, which maybe shared with a bank, an official body or any other party who needs andrequests such statistics with the consent of the user according toprivacy policy agreement. The communication system may present the datain various types of graphical illustrative forms, which may be used formaking management decisions. Furthermore, the communication system mayuse the historical data, and predict future results. For example, basedon crop yields and weather data over a period of time for a parcel ofland, the communication system may predict future crop yields for theparcel of land. The communication system may present the predictions invarious types of graphical illustrative forms on user interfacesassociated with the digital board.

Reference will now be made to the embodiments in the drawings, andspecific language will be used here to describe the same. It willnevertheless be understood that no limitation of the scope of the claimsor this disclosure is thereby intended. Alterations and furthermodifications of the features explained herein, and additionalapplications of the principles of the subject matter explained herein,which would occur to one skilled in the relevant art and havingpossession of this disclosure, are to be considered within the scope ofthe subject matter disclosed herein. The present disclosure is heredescribed in detail with reference to embodiments explained in thedrawings, which form a part here. Other embodiments may be used and/orother changes may be made without departing from the spirit or scope ofthe present disclosure. The embodiments described in the detaileddescription are not meant to be limiting of the subject matter presentedhere.

FIG. 1A shows a communication system 100. The communication system 100may include hardware components and software algorithms, which mayenable interaction between users working on a farm, and aggregate farmoperation data acquired from the users. The farm operation data may beobtained from individual users in a real-time basis. The communicationsystem 100 may process the farm operation data, and generate graphicaldisplays of statistical data of, for example, characteristics and volumeof crop yields, productivity of the soil, productivity of the users, andefficiency of the farm operation. The communication system 100 may allowsharing of the aggregated farm operation data and the processed farmoperation data to third parties, such as, a bank, an official body, orany other counterparty, which may need or request such data.

The communication system 100 may generate useful historical data basedon real-time feed associated with the farm operation data, which may beused for data-driven decision making in a farming context. The farmingcontext and the farming examples described therein are merely exemplary,and should not be construed to limit the scope of this disclosure. Thefarming example is chosen merely for the ease of explanation. Theembodiments disclosed herein are equally applicable to othercollaborative situations, wherein multiple users scattered acrossmultiple locations in any industry may exchange and keep track ofinformation and action items. For instance, the embodiments disclosedherein may be used in various types of industrial operations, such as,vehicle fleet management and warehouse operations.

The communication system 100 may include a first computing device 102(for example, a first farmer device 102), a second computing device 104(for example, a second farmer device 104), a data processing system 106,and a network 108. The data processing system 106 may include a server110, an application programming interface (API 112), and a database 114.

The first computing device 102, the second computing device 104, and thedata processing system 106 communicate with each other over a network108. The server 110 and the database 114 communicate with each otherover the network 108. The network 108 may include, but is not limitedto, private or public local area network, wireless local area network,metropolitan area network, wide-area network, and the Internet. Thenetwork 108 may further include both wired and wireless communicationsaccording to one or more standards via one or more transport mediums.The communication over the network 108 may be performed in accordancewith various communication protocols such as transmission controlprotocol and internet protocol, user datagram protocol, and institute ofelectrical and electronics engineers communication protocols. Thenetwork 108 may further include wireless communications according toBluetooth specification sets, or another standard or proprietarywireless communication protocol. The network 108 may further includecommunications over a cellular network, including, for example, a globalsystem for mobile communications, code division multiple access, andenhanced data for global evolution network.

In operation, a first farmer device, such as, the first computing device102 and a second farmer device, such as, the second computing device 104may share data (such as, farm data) on a digital board accessible via acommon communication application (such as, a farm data sharingapplication) available on the first computing device 102 and the secondcomputing device 104. For instance, the first computing device 102 mayexecute the communication application. A first user may use thecommunication application to generate the digital board. The first usermay assign a second user to the digital board. The first user maygenerate a digital ticket within the digital board. The digital ticketmay include one or more tasks for the second user. The digital ticketmay include one or more instructions and datasets associated with theone or more tasks. The communication application of the first computingdevice 102 may share the digital board and the digital ticket with thecommunication application of the second computing device 104. Thecommunication application of the second computing device 104 may tracklocation of the second computing device 104 operated by the second userwhen the second user is executing the one or more tasks. Thecommunication application of the second computing device 104 may furthertrack status of one or more machines used by the second user to executethe one or more tasks. The communication application of the secondcomputing device 104 may process information associated with the statusof the one or more machines and the location data of the second user todetermine whether the one or more tasks are completed. Upon determiningthat the one or more tasks are completed, the communication applicationof the second computing device 104 may update the digital ticket.Updated digital ticket may include a message that the one or more tasksare completed. The communication application of the second computingdevice 104 may transmit the updated digital ticket to the communicationapplication of the first computing device 102. The first computingdevice 102 may review information associated with the updated digitalticket. The first computing device 102 may parse the informationassociated with the updated digital ticket to review the information.The first computing device 102 may close the updated digital ticket uponconfirming that one or more tasks have been completed by the seconduser.

A first computing device 102 may be a portable or non-portable computingdevice with a processor that performs one or more operations accordingto one or more programming instructions. The examples of the firstcomputing device 102 may include, but are not limited to, a mobilephone, a cellular phone, a tablet computer, a smart watch, a personaldata assistant, a laptop, or a personal computer. The first computingdevice 102 may be capable of communicating with the data processingsystem 106 through the network 108 using wired or wireless communicationcapabilities.

A second computing device 104 may be a portable or non-portablecomputing device with a processor that performs one or more operationsaccording to one or more programming instructions. The examples of thesecond computing device 104 may include, but are not limited to, amobile phone, a cellular phone, a tablet computer, a smart watch, apersonal data assistant, a laptop, or a personal computer. The secondcomputing device 104 may be capable of communicating with the dataprocessing system 106 through the network 108 using wired or wirelesscommunication capabilities.

The first computing device 102 and the second computing device 104 mayinclude one or more input/output devices. The input/output devices maybe configured to allow the user interaction with one or more programs.The programs may be configured to communicate with the data processingsystem 106 to perform exchange and management of the data through theserver 110. The user may have a communication application installed onthe first computing device 102 from which the user may access andinteract with the data processing system 106 to perform exchange andmanagement of the data. The communication application may be a softwarestack running on an operating system of the first computing device 102and the second computing device 104. The communication application mayhave a protocol layer and a user interface layer where each layer may beresponsible for specific functions. The protocol layer may communicatewith the operating system of the first computing device 102 and thesecond computing device 104. The protocol layer may manage theconnections of the first computing device 102 and the second computingdevice 104 over the network 108. The protocol layer may communicate withthe user interface layer. The protocol layer may be arranged to controlthe user interface layer to present the data to the user, via the userinterface of the communication application, on the first computingdevice 102 and the second computing device 104, and to receive the datafrom the user, via the user interface of the communication application,on the first computing device 102 and the second computing device 104.

The user may have the communication application installed on the firstcomputing device 102 and the second computing device 104, from which theuser may access and interact with the server 110, to perform exchangeand management of the data. The user may access features of thecommunication application, via a social networking application, toperform farm data transmission transactions. The social networkingapplication may be a software stack running on an operating system ofthe first computing device 102 and the second computing device 104. Thesocial networking application may have a protocol layer and a userinterface (or a digital board) layer where each layer may be responsiblefor specific functions. The protocol layer of the social networkingapplication may communicate with the operating system of the firstcomputing device 102 and the second computing device 104. The protocollayer may manage the connections of the first computing device 102 andthe second computing device 104 over the network 108. The protocol layermay communicate with the user interface layer. The protocol layer may bearranged to control the user interface layer, to present the data to theuser, via the user interface of the social networking application, onthe first computing device 102 and the second computing device 104, andto receive the data from the user, via the user interface of the socialnetworking application, on the first computing device 102. The protocollayer may communicate with the user interface layer, and may be arrangedto control the user interface layer, to present information to the user,via the user interface of the social networking application, on thefirst computing device 102 and the second computing device 104, and toreceive the data from the user, via the user interface of the socialnetworking application, on the first computing device 102.

The first computing device 102 may run a web browser, which may accessand present a communication application to be executed by a processor ofthe first computing device 102, the second computing device 104, or theserver 110. The first computing device 102 may allow the user to performfarm data exchange and management transactions using the communicationapplication on the first computing device 102 as well as the secondcomputing device 104. The user may execute the communication applicationto present a digital board. The digital board may be accessed togenerate a digital ticket. The digital ticket may include tasks assignedfor multiple users and responses by the multiple users for the assignedtasks. The first computing device 102 and the second computing device104 may execute the communication application outside of a web browser,for example, an operating system-specific communication application,which may access and present processed data. The processor of the firstcomputing device 102, the second computing device 104, or the server 110may process the data to generate the processed data in order to performthe farm data exchange and management transactions.

The first computing device 102 and the second computing device 104 maystore the data associated with the farm information exchange and themanagement transactions, which may be performed by the user, via thecommunication application. The data may be stored in a local databaseassociated with the first computing device 102 or the second computingdevice 104. The data may include, but not limited to, a list ofrecipients, a list of invoices, a list of farm videos, or any othertransaction information transmitted over the network 108 from the firstcomputing device 102 and the second computing device 104. The datawithin the local database may be formatted in accordance with a varietyof different protocols, such as, security and communication protocols.For example, all or a portion of the network 108 may be a packet-based,Internet Protocol network, which may communicate the data from the firstcomputing device 102 and the second computing device 104 to the localdatabase in Transmission Control Protocol/Internet Protocol packets. Inone example, the data may be formatted in accordance with a formattingspecification or protocol expected by the digital board and/or the localdatabase. The processor of the first computing device 102 and/or thesecond computing device 104 may transmit formatted data to the digitalboard and/or the local database.

A local database associated with the first computing device 102, thelocal database associated with the second computing device 104, and thedatabase 114 may be in communication to each other via the network 108.Each database may include a non-transitory machine-readable storagemedia capable of receiving and storing the data associated withoperation and management of the farm. Each database may have a logicalconstruct of data files, which may be stored in a non-transitorymachine-readable storage media, such as, a hard disk or memory,controlled by software modules of a database program (for example, SQL),and a related database management system (DBMS) that executes the codemodules (for example, SQL scripts) for various data queries andmanagement functions generated by the server 110, the first computingdevice 102, or the second computing device 104.

A data processing system 106 may include servers 110. At least some ofthe servers 110 may handle secure data messages and transactions toprocess all the messages with multiple mobile or electronic devices(such as the first computing device 102 and the second computing device104) of the users. A server 110 may be a portable or non-portablecomputing server device with a processor that performs one or moreoperations according to one or more programming instructions. Theexamples of the server 110 may include, but are not limited to, a servercomputer, a personal data assistant, a gaming console, a laptop, or apersonal computer. The server 110 may be capable of communicating withcomponents of the communication system 100 through the network 108 usingwired or wireless communication capabilities. It should be understoodthat the data processing system 106 as shown and described is merelyillustrative and other types of data processing systems should also beconsidered within the scope of this disclosure. For example, the dataprocessing system 106 may use a blockchain (public and/or consortium)for uploading, retrieving, and modifying data records generated in thesystem 100. In some embodiments, the data processing system 106 may usethe blockchain in association with a local database (e.g., database114). In these embodiments, the blockchain may store the hashes of datarecords and the data records (not hashed) may be stored in the localdatabase.

The processor of the server 110 may operate the data processing system106. A single processor of the server 110 may operate the dataprocessing system 106. Multiple processors of the server 110 may operatethe data processing system 106 as a multi-processor system. Theprocessor may include, but not limited to, suitable logic, circuitry,and interfaces, which are operable to execute one or more instructionsto perform data transfer and processing operations. The processor may berealized through a number of processor technologies. The examples of theprocessor may include, but are not limited to, an x86 processor areduced instruction set computing processor, an application-specificintegrated circuit processor, or a complex instruction set computingprocessor. The processor may also include a graphics processing unit,which may execute the set of instructions to perform one or moreprocessing operations.

The processor may process data exchange associated with a digital ticketconducted on a digital board of the computing devices (such as the firstcomputing device 102 and the second computing device 104) of the users.In some cases, the first farmer device (for instance, the firstcomputing device 102) may initiate a message transfer to a second farmerdevice (for instance, the second computing device 104) through theserver 110, via digital board of the communication application, of thedata processing system 106. The data processing system 106 can, based onthe message transfer request, generate instructions to transfer messagebetween a sender digital board to a recipient digital board, and maycommunicate with the sender and recipient mobile or other electronicdevices (such as the first computing device 102 and the second computingdevice 104).

The digital board may be associated with the communication applicationinstalled on the first computing device 102 and the second computingdevice 104. The digital board may be an information sharing platformmanaged by the users of the farm, and may be associated with one or morefield numbers within the farm. The data contained within the digitalboard may be stored at a local database associated with the server 110.The server 110 may communicate with a record server. The server 110 maycommunicate with the record server over an external network 108. Totransfer messages between the digital boards accessible on the senderand the recipient devices, the server 110 may identify permissions onthe accounts of the sender and the recipient devices. The server 110 maysubmit a request to an appropriate record server, to publish andtransfer the message on the digital board. The record server may receiveand process the request by transmitting the message to the digital boardof the appropriate receiver device.

A server 110 may be positioned between the first computing device 102,the second computing device 104, and the record server. The server 110may be part of the data processing system 106, which may also includethe API 112 and the database 114. The server 110 may use the API 112 tocommunicate with the first computing device 102 and the second computingdevice 104 belonging to the users over the network 108. The database 114may include information such a user profile, one or more lists of theusers, and a list of farming fields of the users. In the communicationsystem 100 seen in FIG. 1A, the server 110 may receive transmissionsregarding message requests that occur between the user using the firstand the second computing devices 102, 104, and the record server. Uponreceiving the message transfer and publication request from the user,the server 110 may forward the message to the record server. The recordserver may be hosted by a social media institute or a third party, whichmay provide a service to the communication system 100. The record servermay include, but not limited to, one or more processors to execute oneor more farming tasks of the communication system 100.

In operation, the user may access a communication application of thedata processing system 106 on a graphical user interface of the firstcomputing device 102. The first computing device 102 may have a displayscreen. The display screen of the first computing device 102 mayinclude, but not limited to, a cathode ray tube (CRT) display, a liquidcrystal display (LCD), a plasma, or a light emitting diode (LED)display. The display screen may provide some or all of the functionalityof the graphical user interface of the first computing device 102. Thedisplay screen may be a touch-sensitive or a presence-sensitive display,which may display the graphical user interface, and detect input fromthe user in a form of user input gestures. A graphics subsystem mayreceive textual and graphical information, and process the informationfor output to the display screen. The display screen may include thegraphical user interface, which may allow the user interact with thefirst computing device 102. The examples of the graphical user interfacemay include, but are not limited to, a keypad embedded on the firstcomputing device 102, a keyboard, a mouse, a roller ball, buttons,stylus, or other devices, which may allow the user to interact with thefirst computing device 102. The first computing device 102 may notinclude the graphical user interface, and the user may interact with thefirst computing device 102 with the display screen (e.g., by providingvarious user gestures). The user may interact with the first computingdevice 102 with the graphical user interface and the display screen. Thegraphical user interface may contain multiple portions. Each portion maybe used for a specific purpose, such as, sending and receiving taskmessages via the communication application, generating a task messagevia the communication application, and interacting with a third partyapplication.

Initially, the user may not have an account on the communicationapplication executing on the first computing device 102. The user mayregister on the communication application using a register (sign in)button 2900, as depicted in FIG. 29. The user may register on thecommunication application by generating a username using a full name, aphone number, and/or e-mail address to access the features of thecommunication application. Upon the user completing the sign in process,a button 3000 may be displayed on the graphical user interface of thefirst computing device 102, as illustrated in FIG. 30, to submit a nameof a farm in the communication application. Upon the user submitting thename of the farm or skipping the submission of the farm name for thetime-being, a list of participants (for example, team members) may beadded to the user's account on the communication application, using ainvite button 3100 on the graphical user interface of the firstcomputing device 102, as illustrated in FIG. 31. For instance, the firstcomputing device 102 may contain a list of contacts. The list ofcontacts may include one or more of: name of each recipient user, aphone number of each recipient user, a username associated to therecipient user data sharing application, e-mail address of eachrecipient user, and account details for each recipient user. The list ofcontacts and their corresponding details may be stored on a localdatabase of the first computing device 102 or the database 114. The usermay select at least some of the contacts from the list of contacts andadd the selected list of contacts to their account on the farmcommunication application.

Upon generating an account at the communication application, the usermay then enter login data to access the account. The server 110associated with the communication application may then receive the logindata entered by the user during the signing in process. The server 110may implement a series of security protocols in order to verify that theaccount at the communication application being accessed by the user onthe first computing device 102 belongs to the user. For instance, in oneof the security protocol implemented by the server 110, the server 110may generate a security code that may be transmitted to a phone numberof the user operating the first computing device 102. The server 110 maythen request the user of the first computing device 102 to enter thecode on an interface of the communication application. In one example, acode may include a secret token. The secret token may be a globallyunique identifier, such as, a unique string of characters. The uniquestring of characters may include, but not limited to, letters or numbersor both. In another example, a code may include Uniform ResourceLocators (URLs). The URL may be used to designate an address from whichthe user of the first computing device 102 may obtain instructions andinformation for logging into the account. The code may be associatedwith an expiry time. The expiry time may be included in the code. Theexpiry time may be recorded together with the secret token associatedwith the code at the database 114 when the code is generated.

The user upon logging into the account in the communication applicationon the first computing device 102 may generate a digital board and atask, using a create board button 3206 and a create task button 3204presented on the communication application being executed on the firstcomputing device 102, as illustrated in the FIG. 32. A first useroperating the computing device 102 may generate or select one or moretasks on the digital board to be completed by a second user operatingthe second computing device 104. The digital board may be accessible tothe users (such as the first user and the second user) of both the firstcomputing device 102 and the second computing device 104, via thecommunication application. The digital board may display the tasks toall other users, which the other users may view on same digital board oftheir farm communication application. The digital board may display allthe tasks created by all other users that are registered as participantsof the digital board for each other to execute.

A first non-limiting example of a task generated on a digital board by afirst user operating a first computing device 102 may be a request for asecond user operating a second computing device 104 to fertilize fieldson a specific location in a particular field of the farm. As depicted inFIG. 33, a fertilize field task 3302 may be displayed on the digitalboard associated with the farm communication application being executedon the computing devices of the first user and the second user. A secondnon-limiting example of a task generated on a digital board by the firstuser operating the first computing device 102 may be a request for thesecond user operating the second computing device 104 to count a numberof cattle in the fields. As depicted in FIG. 33, a general task 3304associated with a count of cattle may be displayed on the digital boardassociated with the farm communication application being executed on thecomputing devices of the first user and the second user. A thirdnon-limiting example of a task generated on a digital board by the firstuser operating the first computing device 102 may be a request for thesecond user of the second computing device 104 to wait until apre-defined date and time in order to send invoices. As depicted in FIG.33, a notes task 3306 displayed on the digital board associated with thefarm communication application being executed on the computing devicesof the first user and the second user may require the second user towait until a pre-defined date (for example, the end of the day) in orderto transmit the invoice. A fourth non-limiting example of a taskgenerated on a digital board by the first user operating the firstcomputing device 102 may be a request for the second user of the secondcomputing device 104 to wait until a pre-defined date and time to have astaff meeting. As depicted in FIG. 34, a meeting task 3402 displayed onthe digital board of the devices of the first user and the second usermay require the second user to wait until a pre-defined date (forexample, every week) in order to attend or coordinate a staff meeting.

Upon logging into the communication application on the first computingdevice 102, a first user may generate a task message on a digital boardcomprising at least one task for a second user operating the secondcomputing device 104. As depicted in FIG. 35, a task 3502 displayed onthe digital board associated with the farm communication applicationbeing executed on the computing devices of the first user and the seconduser may require the second user to measure yield data. The task messagemay include one or more items for the second user. For example, thefirst user of the first computing device 102 may select the items, suchas, an image, a video file, a file document, or any suitable informationfrom a local database of the first computing device 102. The selecteditem may be a gift item offered by the first user to the second user,and may be a product or service offered by one or more retailers.Examples of the items that may be selected include a virtual item, suchas, an electronic movie ticket, digital song or gaming content. Theexamples of the items that may be selected include real gifts couponsassociated with, but not limited to, a tangible item, such as: books,food items, consumer products, and other physical good; and a servicecoupon such as a spa treatment. Other examples of the items that may beselected may be associated with an intangible item, such as, monetarycredit and gift points, redeemable at a particular retailer or group ofretailers.

A first user of the first computing device 102 may arrange digitalboards within the communication application, and tasks within thedigital boards in a pre-defined order for display on the graphical userinterface associated with the communication application. The first userof the first computing device 102 may arrange the digital boards and thetasks in the pre-defined order, for display on the graphical userinterface of the computing devices of other users, where other users areparticipants of the digital boards. As depicted in the FIG. 36,templates 3602 may be displayed on the graphical user interface of thefirst computing device 102, which may be selected by the first user togenerate digital boards. The templates for creating the digital boardmay include a chat template, a measure template, a task template, aphoto template, an event template, a reminder template, and a notetemplate. Upon the creation of the digital boards, the first user of thefirst computing device 102 may then arrange the created digital boardsin the pre-defined order within the communication application. Thedigital boards may appear in a pre-defined order in communicationapplication accounts of the users who are registered to access thedigital boards.

Upon the creation of the digital boards, a first user may edit thedigital boards, as depicted in the FIG. 37A, to add a board name 3702,to add a list of participants 3704, to add a date and time for tasks3706, and to add an action task 3708. For example, as shown in the FIG.37B, a first user may select a name button 3710 on the graphical userinterface associated with the communication application being executedon a first computing device 102 to add a name for the created digitalboard. Then in order to add participants who may have access to the datawithin the digital board or an ability to share data on the digitalboard, the first user may select add participant button 3712 on thegraphical user interface associated with the communication application,as shown in FIG. 37C, to add the participants for the digital boards.The first user may further use a date/time button 3714 on the graphicaluser interface associated with the communication application, as shownin FIG. 37D, to add a date and time information for execution of thetasks in the digital boards. The first user may further use an actionbutton 3716 on the graphical user interface associated with thecommunication application, as shown in FIG. 37E, to add an action (or atask) and detailed information associated with the task in the digitalboards. Upon the creation of the digital board, a first user may beprovided a summary of the information associated with each digitalboard. For instance, a first user may select a button 3718 on thegraphical user interface associated with the communication application,as shown in FIG. 37F, to view a summary of the digital board (associatedwith yield for field 17). In some cases, a first user may be provided ahistory of operations associated with each digital board. For instance,a first user may select a button 3802 on the graphical user interfaceassociated with the communication application, as shown in FIG. 38A, toview a history of summary of the digital board (associated with yieldfor field 17). Upon the selection of the button 3802 on the graphicaluser interface associated with of the communication application, then asnapshot 3804 of history is displayed on the digital board presented onthe communication application, as depicted in FIG. 38B.

The snapshot 3804 of history may be a graphical user interface that mayinteractively and graphically display historical data associated with afarming operation. As shown herein, the snapshot 3804 may display dailycrop yield of field over a period of time. Within the snapshot 3804, aninteractive graph may include a bar chart showing the numerical dailyyield over a period of time and a line chart showing the daily change inthe yield. At the top of the graph, the snapshot 3804 may includenumerical values indicating the latest yield, average yield, and apercentage change in the yield in the past twenty-four hours. Thesnapshot 3804 is merely exemplary and the system may present historicaldata in other forms and formats. Furthermore, a user may share datadisplayed on the snapshot 3804 to other users or entities. In someinstances, the other users or other entities may access the data in thesnapshot based on permission controls selected by the user. In someinstances, the sharing the data may be based upon agreements between theuser and the other users and entities. The agreements may be implementedin software at both the application level in the devices and theback-end computer infrastructures. In some embodiments, the sharing ofthe data may be based upon the conditions for participation. Forexample, if a new user wants to collaborate with the user, data sharingmay be a pre-condition for the new user to participate. In someembodiments, an application provider, i.e., the entity providing thedevice application and maintaining the back-end computer infrastructure,may also impose these conditions for every user who downloads and usesthe application.

The historical data displayed in the snapshot 3804 or any other type ofgraphical user interface may indicate the overall attributes of afarming operation. For example, the historical data may indicate thevolume and characteristics of the yield for different fields and theoverall farm. The historical data may indicate the overall health of thelivestock in the farm. The historical data may indicate which breed ofcattle or which variety of a crop is successful. As another example, thehistorical data may display the productivity of various workers in thefarm. For the farmer, the historical data at the fingertips will enableinformed and data driven decisions as opposed to the conventionalmethods when none of these functionalities were available to the farmer.It should however be understood that the aforementioned examples ofhistorical data are merely illustrative, and other examples ofhistorical data should be considered within the scope of thisdisclosure.

The historical data may allow other entities to evaluate the overalloperation of the farm. For example, a bank willing to provide anexpansion loan to the farm may access the historical data to determinewhether the farm may be able to pay back the loan. A regulatory entitymay access the historical data to ensure that the farm is complaint withthe relevant regulations. The regulatory authority may access thehistorical data in accordance with the user consent and the privacy lawsof the jurisdictions where the system 100 is used. An appraiser mayaccess the historical data to properly appraise the farm. In otherwords, the embodiments disclosed herein leverage the real-time datacollection by various workers in the farm to generate an accuratehistorical profile that can be used to make informed, data-drivendecisions.

Upon the creation of digital boards and digital tickets comprising tasksfor display in each digital board, the first computing device 102 mayelectronically transmit task messages containing the tasks to computingdevices of recipient users. The task messages may then be displayed onthe graphical user interface associated with a farm communicationapplication running on their computing devices in a pre-defined order.The task messages may be displayed on a digital board accessible fromthe communication application running on the computing devices of therecipient users. In one example, a task displayed in a task message maybe a request for the recipient user to go to a specific location in thefarm to execute the task. The first computing device 102 may track acurrent location of the computing device of the recipient user using aGlobal Positioning System satellite system. The Global PositioningSystem satellite system is a network of plurality of satellites that isused to determine a location of an antenna of the computing device ofthe recipient user that receives signals from a number of satellites ofthe Global Positioning System satellite system. The computing device ofthe recipient user may itself track its current location using alocation services application. The set of tasks displayed in a taskmessage may include a first set of tasks and a second set of tasks. Uponcompletion of the first set of tasks, the recipient user may obtaininstructions for the second set of tasks, and upon completion of thesecond set of tasks, the recipient user operating the recipientcomputing device may obtain a reward. Each of the first and second setof tasks may have a separate set of instructions and timelines forexecution by the recipient user operating any computing device, forexample, the second computing device 104.

FIG. 1B shows a digital board 116, which will be explained inconjunction with a communication system 100 of the FIG. 1A. Embodimentsof the communication system 100 may provide a digital ticketfunctionality to facilitate transactions and information sharing acrossmultiple users. The communication system 100 may provide a digital boardfunctionality where the digital board 116 may be a container for digitaltickets 118. The digital board 116 containing the digital tickets 118may be implemented by the communication system 100 within acommunication application. A digital ticket 118 may allow multiple usersto share information, data, and/or media and enable transactions. Thedigital ticket 118 may enable a “request-response” mechanism, wherein afirst user may input a request for some information to trigger a seconduser to respond with the requested information through the ticket 118initiated by the first user. The first user may manually input data tothe digital ticket 118. In addition, a third party may utilize anapplication programming interface provided by the system toautomatically input data to the digital ticket 118.

The digital ticket 118 may represent a unique transaction that may carrya specific dataset of information. Multiple digital tickets 118 mayenable multiple transactions as a sequence of tickets 118 a, 118 b, 118c, 118 d, 118 e, 118 f tied together within the digital board 116. Thedigital ticket 118 may distribute any type of digital content, data,and/or media. Furthermore, the digital ticket 118 may have a dedicatedmessaging feature that may enable the users associated with the digitaltickets 118 to communicate with each other. The digital ticket 118 maybe of one type among multiple types. Some types of the digital ticket118 are described in the following paragraphs.

A digital ticket 118 may be a measurement ticket, which may provide afunctionality of measuring, counting, and keeping track of numberswithin the application. For example, a first user (requester) may createthe measurement ticket for a second user (receiver) by choosing a nameform a list of users previously invited into the application. The firstuser may name the measurement ticket and may define a specific requiredunit of measure. Non-limiting examples of the unit of measure includecentimeter (cm), liter (1), kilometer (km), and hectare (ha). The firstuser may also specify a number format such as whole number, percentage,and/or decimal. The first user may also set a time for the measurement,for example, a specific date and hour. The first user may configure themeasurement ticket to repeat at predetermined time intervals. Forexample, the first user may configure the measurement ticket to repeatdaily, weekly, or monthly.

The second user may receive a notification of the measurement ticket inthe communication application and/or a device running the communicationapplication. The measurement ticket may provide an input field in the“TO DO” screen of the communication application. The second user mayinput a measurement number in the measurement ticket. The first user mayreceive a notification of the input, and may view the input in a homescreen of the continuation application. Each of the first and the secondusers may view the historical data records a graph since the creation ofthe measurement ticket.

A digital ticket 118 may be a checklist ticket, which may be a requestof action. A first user may instantiate a checklist ticket to set tasksand to-do lists for other users or for herself. The process steps ofcreating the checklist ticket may be similar to the process of creatinga measurement ticket as described above. The checklist ticket mayinclude identification information of a second user (receiver), name ofthe ticket, date of the ticket creation, and checklist with descriptionof items. Once the first user creates the checklist ticket, the seconduser may receive a notification on an application or a phone. The seconduser may view the checklist ticket and the tasks requested to actiontherein in a “TO DO” screen displayed by the application. The seconduser may flag each task once completed in the checklist ticket and sharethe information, via the checklist ticket, with the first user, who willreceive a notification in the home screen of the application.

A digital ticket 118 may be an event ticket that may contain a requestfor a meeting that may be scheduled within a schedule of a “TO-DO”screen. The digital ticket may be a reminder ticket that may allow usersto set reminders for themselves or other selected users. The digitalticket 1202 may also be a third party ticket that may allow a user toconnect with other sources of data, content, and/or media. The user mayhave access to third party tickets associated with, for example, weatherforecast, news, markets and commodity prices, sensor-powered data feeds,and/or Internet of Things data sources. It should be understood that theaforementioned digital tickets 118 are merely illustrative and othertypes of digital tickets 118 should be considered within the scope ofthis disclosure. Other illustrations of digital tickets 118 may include,for example, a purchase request or record, a payment request or request,production of an invoice, and a request for advisory.

As described above, the digital board 116 may be the container of thedigital tickets 118. A set of related digital tickets 118 may beattached to a specific digital board 116, which may be repository ofdata, content, and/or media for a specific subject matter. The user maygenerate the digital board 116 without any limits on subject, data,industry needs, personal needs, and/or business needs. The digital board116 may be a framework to connect people with associated transactions.The user may create the digital board 116 by defining a name and addingusers to the digital board 116. The user may choose selecting among agroup of users previously invited to use the application. The user mayalso access her phone's contact list to invite other users to thedigital board 116. Users participating in the digital board 116 mayaccess data, content, and or media present in the board. Furthermore,the digital board 116 may have a dedicated messaging feature that mayenable the participating users to communicate among themselves.

FIGS. 2A-27C show an interactive graphical user interface (or aninteractive dashboard) showing a webpage of a communication applicationexecuting on a computing device by a user. The computing device may be aportable or a non-portable device, such as, a mobile phone, a laptopcomputer, a tablet computer, a smart phone, or the like. The computingdevice may include a processor, which may perform one or more operationsaccording to one or more programming instructions. The computing devicemay be capable of communicating with a data processing system, through acommunications network, using wired or wireless communicationcapabilities.

The communication application may be a software application installed onthe computing device. The communication application may be displayed ona user-centric website accessible via the computing device. A companymay generate the communication application as a widget to enablecommunication between different types of users, such as, farmers workingon different field locations. The widget may be displayed on a websiteof the company, which may be visible to all the users.

The computing device may have access to pre-stored web-based interfaces,such as, webpages, which may include a number of preconfiguredsub-interfaces, or containers, that are dynamically populated (e.g.,widget box). For example, the webpages associated with the communicationapplication may contain code, such as, Hyper Text Markup Language,presenting a website of a number of webpages having a uniquelook-and-feel. One or more outputs may display the webpages, which maycontain additional code for the containers, where the container codedisplays the widget of the communication application.

Initially, a user may download and open a communication application (forexample, a farm data management application) on a computing device. Uponopening the communication application, webpages 200, 202, and 204associated with the communication application may be displayed on thegraphical user interface of the computing device, as depicted in theFIGS. 2A-2C. The webpages 200, 202, and 204 may display informationassociated with introduction section of the communication application.The information may include data about all features associated with thecommunication application.

The user may not have an account on the communication application. Theuser may register on the communication application using a “sign in”button 300, as depicted in FIGS. 3A and 3B. The “sign in” button 300 isdisplayed on a webpage associated with the communication application.The user may register on the communication application using a phonenumber 302. The user may submit the phone number. A server associatedwith the communication application may implement a series of securityprotocols in order to verify the phone number of the user. For instance,in one of the security protocol implemented by the server, the servermay generate a security code that may be transmitted to the phone numberof the user. The server may request the user to enter the code in a box400, as depicted in the FIGS. 4A and 4B, on the webpage associated withthe communication application. The code may be associated with an expirytime. The expiry time may be included in the code.

User registration process may further include the user submitting ausername in a box 500, as depicted in FIG. 5. The box 500 is displayedon the webpage associated with communication application. Upon the usercompleting the registration and sign in process, a home page 600 of thecommunication application may be displayed on the computing device, asdepicted in FIGS. 6A and 6B. The home page 600 may be a home screenwebpage of a user account on the communication application. The homescreen webpage may operate as a main navigation page with a “pop-up”menu with multiple selectable graphical components. The user may use thehome screen webpage to do certain actions from the home screen webpage,via the selectable graphical components, such as, creating tickets,searching for tickets to submit, create boards, invite members, creatingtickets from the user library.

When the user interacts with the multiple selectable graphicalcomponents, multiple interactive icons 604 may be displayed on the homepage 600. The multiple interactive icons 604 may include an icon toinvite someone, an icon for instant ticket, an icon for new ticket fromlibrary, an icon for new ticket, and an icon for new board. The user mayalso be able to enter their location, and have a weather card display602 on the top of the home screen webpage.

The user may execute instructions on the computing device to interactwith the selectable graphical components to customize the dashboardassociated with the communication application. During the customizationprocess of the dashboard, the user may include a section 700 for aninternal team summary, a section 702 for a log book of the user, and asection 704 for test information of the user, as depicted in FIGS. 7A,7B, and 7C, in the dashboard. The section 702 may be for a digitalrecordkeeping.

The user may interact with an interactive icon 800 associated with afield to invite someone, as depicted in the FIG. 8A. The interactiveicon 800 is displayed on the webpage associated with the communicationapplication. The user may invite a list of participants (for example,team members) to add to the user's account, using a search button 802,as showed in the FIGS. 8B and 8C. The search button 802 is displayed onthe webpage associated with communication application. The computingdevice may contain a list of contacts. The list of contacts may includeone or more of: name of each recipient user, a phone number of eachrecipient user, a username associated to the recipient user, e-mailaddress of each recipient user, and account details for each recipientuser. The user may select at least some of the contacts from the list ofcontacts, and add selected list of contacts to their account on thecommunication application. A list of existing members 804 and newcontacts may then be displayed on the dashboard associated with thecommunication application, as depicted in the FIG. 8D.

The user may interact with an interactive icon 900 associated with afield for submit an instant ticket, as depicted in the FIG. 9A. Theinteractive icon 900 is displayed on the webpage associated with thecommunication application. The submit instant ticket interactive icon900 may allow a user to select a ticket (an instant ticket) that may beresubmitted. The instant ticket may not have a due data and a schedule,and may be submitted on-demand. A section 902 for searching new ticketsmay then be displayed on the dashboard associated with the communicationapplication, as depicted in the FIGS. 9B and 9C. The user may use thesection 902 to input terms to search for the tickets.

The user may interact with an interactive icon 1000 associated with afield for a new ticket from library, as depicted in the FIG. 10A. Theinteractive icon 1000 is displayed on the webpage associated with thecommunication application. A section 1002 for searching new tickets fromthe library may then be displayed on the dashboard associated with thecommunication application, as depicted in the FIG. 10B. The user may usethe section 1002 to input terms to search for the new tickets from thelibrary. A copy of the new ticket 1004 may then be displayed on thedashboard, as depicted in the FIG. 10C. The information associated withthe new ticket 1004 may include names of users assigned to the newticket 1004.

The user may interact with an interactive icon 1100 associated with afield for new ticket, as depicted in the FIG. 11A. The interactive icon1100 is displayed on the webpage associated with the communicationapplication. The user may then generate new tickets (such as, digitaltickets). The new tickets may include information associated with one ormore tasks, and instructions associated with the one or more tasks. Theone or more tasks may be assigned to one or more users. A new ticket maybe assigned a ticket name 1102, as depicted in the FIG. 11B. The usermay store the new ticket in a local database (e.g., a local library)associated with the computing device. The new ticket may be assigned toan assignee name 1104, as depicted in the FIG. 11C. The new ticket maybe assigned to a board 1106, as depicted in the FIG. 11D.

After generating the new ticket, the user may generate multiple tasksfor multiple users. The user may include information associated with themultiple tasks in the new ticket. The user may assign a date and a timefor completion of the multiple tasks. The user may interact with a“time” button 1200 and a “due date” button 1202 to submit the date andthe time information associated with the multiple tasks, as depicted inthe FIGS. 12A, 12B, and 12C. The “time button” 1200 and the “due date”button 1202 may be displayed on the webpage associated with thecommunication application. The user may interact with a “repeat” button1200 to submit information associated with repetition of the multipletasks, as depicted in the FIGS. 12D and 12E. In one example, the usermay configure each ticket to repeat each task at predetermined timeintervals. In another example, the user may configure each ticket torepeat daily, weekly, or monthly.

The user may use a “create ticket” button 1300 to create a measurementticket. The “create ticket” button 1300 is displayed on the webpageassociated with the communication application, as depicted in the FIGS.13A-13C. The measurement ticket may provide a functionality ofmeasuring, counting, and keeping track of numbers within thecommunication application. The user may create the measurement ticketfor a second user by choosing a name from a list of users previouslyinvited into the application. The user may submit a name for themeasurement ticket. The user may define a specific required unit ofmeasure. The unit of measure may include centimeter (cm), liter (1),kilometer (km), and hectare (ha). The user may select a number format1302 for the measurement ticket. The number format 1302 is displayed onthe webpage associated with the communication application. Using thenumber format 1302, the user may specify a format, such as, a wholenumber, a percentage, or a decimal. The user may set a time for themeasurement, for example, a specific date and hour. The user mayconfigure the measurement ticket to repeat at predetermined timeintervals. For example, the user may configure the measurement ticket torepeat daily, weekly, or monthly. The new ticket including themeasurements 1304 may then be displayed on the dashboard associated withthe communication application.

The user may use a “create ticket” button 1400 to create a checklistticket, which may be a request of an action. The “create ticket” button1400 is displayed on the webpage associated with the communicationapplication, as depicted in the FIGS. 14A-14B. The user may instantiatethe checklist ticket to set tasks and to-do lists for other users or forthemselves. The checklist ticket may include identification informationof receiver users, a name of the checklist ticket, a date of thechecklist ticket creation, and description of checklist items 1402. Oncethe user creates the checklist ticket, the recipient user may receive anotification on their computing device. The recipient user may view thechecklist ticket on their computing device.

The user may interact with a “new board” button 1500 from a pop-up menuto create a new board. The “new board” button 1500 is displayed on thewebpage associated with the communication application, as depicted inthe FIGS. 15A-15C. The new board may include multiple tickets. The newboard may include one or more tasks associated with each ticket. Theuser may have a choice to add participants 1502 to the board. The usermay add participants 1502 to the board when required. The user mayselect a name for the board, and enter the name in a name box 1504.

The user may be able to view the name of the boards 1600 they are partof, as depicted in the FIGS. 16A-16B. Also, the user may be able to markthe board using the “star” button 1602 that are very important to theuser. The marked boards are displayed permanently on a board screen andabove the other boards that are created.

The user may interact with a “profile” button 1700 to access theirprofile information, as depicted in the FIGS. 17A-17B. The “profile”button 1700 is displayed on the webpage associated with thecommunication application. The profile information may include a nameand a phone number. The user may interact with an “edit” button 1702 toedit their profile, such as, the display picture. The user may be ableto change the username and the language for the communicationapplication. The “edit” button 1702 is displayed on the webpageassociated with the communication application.

The user may be able to add additional users to their account on thecommunication application, as depicted in the FIGS. 18A-18C. The usermay search for the users to be added to their account using a search box1800. The search box 1800 is displayed on the webpage associated withthe communication application.

The user may interact with a “settings” button 1900 to view multiplesettings, such as, workspace setting and notification setting. The“settings” button 1900 is displayed on the webpage associated with thecommunication application, as depicted in the FIGS. 19A-19D. The usermay interact with a “workspace setting” button 1902 to assign a name tothe workspace, manage members, and manage permission. The “workspacesetting” button 1902 is displayed on the webpage associated with thecommunication application. The user may interact with a “manage members”button 1904 to add members to the workspace, assign members roles, andremove members from the workspace. The “manage members” button 1904 isdisplayed on the webpage associated with the communication application.

The user may interact with a “settings” button 2000 to view multiplesettings, such as, workspace setting and notification setting. The“settings” button 2000 is displayed on the webpage associated with thecommunication application, as depicted in the FIGS. 20A-20C. The usermay interact with a “workspace setting” button 2002 to assign a name tothe workspace, manage members, and manage permissions 2004. The“workspace setting” button 2002 is displayed on the webpage associatedwith the communication application. The managing of permissions 2004 mayinclude editing the permissions for the users with certain roles withinthe workspace.

The user may interact with a “settings” button 2100 to view multiplesettings, such as, workspace setting and notification setting. The“settings” button 2100 is displayed on the webpage associated with thecommunication application, as depicted in the FIGS. 21A-21B. The usermay interact with a “notification setting” button 2102 to edit the typeof notifications the user may receive, and also give the user theability to turn certain notification setting on or off. The“notification setting” button 2102 is displayed on the webpageassociated with the communication application.

The user may interact with an “add workspace” button 2200 to add newworkspaces. The “add workspace” button 2200 is displayed on the webpageassociated with the communication application, as depicted in the FIGS.22A-22D. The user may submit the name of the new workspaces in a namebox 2202. The name box 2202 is displayed on the webpage associated withthe communication application. The user may add new users for each newworkspace. The user may search for the new users using a search box2204. The search box 2204 is displayed on the webpage associated withthe communication application.

The user may interact with “to do” button 2300, which may result indisplaying all tickets assigned to the user. The “to do” button 2300 isdisplayed on the webpage associated with the communication application,as depicted in the FIGS. 23A-23D. The user may view informationassociated with all the tickets on the dashboard 2302 of the computingdevice. When a particular ticket is displayed on the dashboard 2302, theuser may press on a ticket name, and access detailed informationassociated with the particular ticket. The user may interact with a“manage ticket” button 2304 to manage information associated with anyticket. The “manage ticket” button 2304 is displayed on the webpageassociated with the communication application. Upon the interaction withthe “manage ticket” button 2304, one or more icons may be displayed onthe webpage associated with the communication application. The icons mayinclude an edit ticket icon 2306. The user may select or interact withthe edit ticket icon 2306 to edit any information associated with theticket.

The user may interact with “boards” button 2400, which may result indisplaying all boards assigned to the user. The “boards” button 2400 isdisplayed on the webpage associated with the communication application,as depicted in the FIGS. 24A-24C. The user may interact with “big plus”button 2402 to add new boards, participants 2404 in each new board, andname each board using a name box 2406.

The user may interact with “boards” button 2400, which may result indisplaying all boards assigned to the user. The “boards” button 2400 isdisplayed on the webpage associated with the communication application,as depicted in the FIGS. 25A-25C. A user may select a particular board.All information associated with the particular board may then bedisplayed on a dashboard 2502. The information may include all ticketsplaced on the board, the name of users who have completed tasksassociated with the tickets, the name of the tasks that have beencompleted, etc. The information may further include messages 2504 sentby the users to each other.

The user may interact with “to-do” button 2600 and “done” button 2602.The “to-do” button 2600 and the “done” button 2602 may be displayed onthe webpage associated with the communication application, as depictedin the FIGS. 26A-26C. When the user interacts with the “to-do” button2600, all pending tasks are displayed on the dashboard 2604. The tasksare assigned to one or more other users. When the user interacts withthe “done” button 2602, all completed tasks are displayed on thedashboard 2606. The tasks are completed by the one or more other users.

When the user completes a task associated with a ticket, a status of theticked is updated to mention complete. The user interacts with the“done” button 2700 to display the completed ticket on the computingdevice, as depicted in the FIGS. 27A-27D. The “done” button 2700 may bedisplayed on the webpage associated with the communication application.The user may further interact a “view ticket” button 2702 to view allthe information of the completed task associated with the completedticket on the dashboard 2704. The “view ticket” button 2702 may bedisplayed on the webpage associated with the communication application.The user may further interact with an “export now” button 2706 to exportthe information associated with the completed task. The user may submitthe email address to export the information. When the information isexported to the email address, a confirmation message is displayed onthe dashboard 2708.

FIG. 28 shows execution steps for enabling interaction between usersexecuting one or more tasks at one or more locations, according to amethod 2800. The method 2800 shown in FIG. 28 may include executionsteps 2802, 2804, 2806, 2808, 2810, 2812, and 2814. However, it shouldbe appreciated that other embodiments may comprise additional oralternative execution steps, or may omit one or more steps altogether.It should also be appreciated that other embodiments may perform certainexecution steps in a different order; steps may also be performedsimultaneously or near-simultaneously with one another. In addition, themethod 2800 of the FIG. 28 is described as being executed by a firstcomputer and a second computer in this embodiment. The first computerand the second computer executing one or more steps may be programmed toexecute various other, unrelated essential features.

In a first step 2802, a first computer operated by a first user maygenerate a digital board. The digital board may be an informationsharing platform. The digital board may be associated with a farmproject within a workspace associated with a first type of farmoperation. The first type of farm operation may be a field fertilizingoperation. The farm project may be associated with pouring two specifictypes of fertilizers in the field. The two specific types of thefertilizers may be a first fertilizer and a second fertilizer.

The first computer may include a first instance of an application. Thefirst instance of the application may be a mobile or a desktop versionof the application installed on the first computer. The application maybe a communication application for enabling interactions between theusers working at one or more locations. The application may be asoftware program. The users may be farmers working in one or more farms.

The first user of the first computer may submit a first set ofinstructions to the application on the first computer. The applicationmay process the first set of instructions. The application may thengenerate the digital board associated with the farm project. The user ofthe first computer may submit a second set of instructions to theapplication on the first computer. The application may process thesecond set of instructions. The application may then generate a digitalticket within the digital board. The digital ticket may be associatedwith a farm task. The farm task may be associated with the farm project.The farm task may be to pour the two specific types of fertilizers inthe farm field at a particular time of the day. For example, the farmtask may be to pour the first fertilizer in the field at 2 PM and 5 PMeach day, and to pour the second fertilizer in the field at 1 PM and 3PM each day. The farm task may further include information associatedwith an amount of the first fertilizer and the second fertilizer to bepoured each day in the farm field.

The digital ticket may include a data template. The data template may beconfigured to receive data records associated with the farm task. Thedata records may be submitted by the first user of the first computer.The data records may include the name of the fertilizers to be pouredinto the farm field, the name of the users assigned to pour thefertilizers in the farm field, the quantity of the fertilizers to bepoured in the farm field, and the date and time at which the fertilizershave to be poured in the farm field. The first computer may store theinformation associated with the digital ticket in a local databaseassociated with the first computer. The first computer may further storethe digital board, which may include the digital ticket in the localdatabase.

In a next step 2804, the application associated with the first computermay transmit the digital ticket to the application in a second computer.The application in the first computer and the second computer is a samecomputer application. In one embodiment, the first user of the firstcomputer may generate and execute a third set of instructions, which mayresult in the application of the first computer transmitting the digitalticket to the application in the second computer over the wirelessnetwork. In another embodiment, when the first user generates thedigital ticket, the first computer may parse information within thedigital ticket. Based on review of the parsed information, the firstcomputer may instruct its application to transmit the digital ticket tothe application running on the second computer over the wirelessnetwork.

The second computer may be operated by a second user. The secondcomputer may include a second instance of the application. The secondinstance of the application may be a mobile or a desktop version of theapplication installed on the second computer. The application may be asoftware program. The application may be the communication applicationfor enabling interactions between users (the first user and the seconduser) located at different locations.

In a next step 2806, the application associated with the second computermay receive the digital ticket transmitted by the application in thefirst computer. The second computer may store the digital ticket in alocal database associated with the second computer. The second computermay parse information within the digital ticket. The second computer maythen determine all the information associated with the digital ticket.The information may include the name of the fertilizers to be pouredinto the farm field, the quantity of the fertilizers to be poured in thefarm field, the date and time at which the fertilizers have to be pouredin the farm field, and the location coordinates of the farm field.

When the application in the second computer receives the digital ticket,the application in the first computer may activate the digital ticket.In some embodiments, when the application in the second computerreceives the digital ticket, the second user may execute instructions toactivate the digital ticket. When the digital ticket is activated, theapplication in the second computer may start to continuously trackgeolocation data of the second computer when the second user moves alongwith the second computer. A processor of the second computer may storethe geolocation data associated with the second computer in the localdatabase. The second computer may compare the geolocation dataassociated with the second computer with the location coordinates of thefarm field present in the digital ticket. Based on the comparison, whenthe second computer may determine that the second computer is at thelocation coordinates of the farm field, the application of the secondcomputer may generate a notification. The notification may indicate thatthe second user operating the second computer is at the location of thefarm field. The second computer may store the notification in the localdatabase.

The second computer may include a global positioning system receiver orother similar component for determining the geolocation of the secondcomputer. The global positioning system receiver in the second computermay enable the application, which is location-aware to allow the seconduser to search for information based on their location, to find theirplace in a map, or to share their location with other users (such asfirst user) associated with the application.

The global positioning system receiver may be kept engaged tocontinuously update the location of the second computer while the seconduser carry the second computer to various places within the workspace.The continuously engaged global positioning system receiver may allowthe application to utilize the real-time location of the secondcomputer. The real-time location of the second computer, which may bethe location of the second user, may be continuously tracked and shared,rather than other users (such as the first user) manually checking inthe location of the second user intermittently.

In a next step 2808, the application associated with the second computermay continuously retrieve dispensing data through an applicationprogramming interface of a farm machinery associated with the farm task.In some embodiments, the farm machinery may continuously transmit thedispensing data to the application in the second computer when anydispensing activity occurs.

The farm machinery may be a machine, which may be used to dispense thefirst fertilizer and the second fertilizer in the farm field. A samemachine may be used to dispense the first fertilizer and the secondfertilizer in the farm field. The same machine may have two compartmentsto store each of the first fertilizer and the second fertilizer, whichmay dispended in the farm field. In some cases, two separate machinesmay be used to dispense the first fertilizer and the second fertilizerin the farm field. A first machine may be used to dispense the firstfertilizer in the farm field. A second machine may be used to dispensethe second fertilizer in the farm field.

The machine may be an electronic dispenser. The electronic dispenser mayinclude a dispensing application. The dispensing application may be asoftware program. The dispensing application may be linked to theapplication on the second computer. The dispensing application may belinked to the application on the first computer. The linking between thedispensing application and the application on the second computer mayresult in sharing of data between both the dispensing application andthe application on the second computer. The linking between thedispensing application and the application on the first computer mayresult in sharing of data between both the dispensing application andthe application on the first computer. The data may include a name ofthe fertilizer being dispensed out of the electronic dispenser. The datamay include an amount of fertilizer being dispensed out of theelectronic dispenser. The data may further include a timestamp at whichthe fertilizer was dispensed out of the electronic dispenser. The datamay further include location information at which the fertilizer wasdispensed out of the electronic dispenser. In some embodiments, themachine may be a diesel pump and the application in the second computermay retrieve the diesel dispensing data from the diesel pump.

In a next step 2810, the application associated with the second computermay receive the dispensing data from the dispensing applicationassociated with the farm machinery. The second computer may store thedispensing data from in the local database. The application associatedwith the second computer may process information associated with thedispensing data and the geolocation data. The application associatedwith the second computer may update the digital ticket based on theprocessing of the information associated with the dispensing data andthe geolocation data. For example, the application associated with thesecond computer may update the digital ticket to include informationassociated with the farm task. The information may include a date and atime at which the second computer operated by the second user waspresent at the location of the field, which is associated with the farmtask. The information may further include the amount of fertilizersdispensed at the field by the second user. The server computer may storeupdated digital ticket in the local database.

In a next step 2812, the application associated with the second computermay determine a status of the farm task associated with the digitalticket based upon the continuous updates to the digital ticket. Theapplication associated with the second computer may retrieve the updateddigital ticket from the database. The application associated with thesecond computer may parse data associated with the updated digitalticket. The application associated with the second computer may comparethe parsed data with the information associated with the farm task.

When the application associated with the second computer may determinethat the second user has completed the farm task based on the results ofthe comparison operation, in a next step 2814, the applicationassociated with the second computer may generate a final updated digitalticket. The final updated digital ticket may include a message that thefarm task is completed by the second user. The message may includeinformation associated with the completed farm task. The applicationassociated with the second computer may further generate a notificationfor the first user that the farm task is finished. The applicationassociated with the second computer may transmit the notification andthe final updated digital ticket to the application associated with thefirst computer. The application associated with the second computer maytransmit the notification to a phone number associated with the firstcomputer. The application associated with the second computer maytransmit the notification to an electronic mail associated with thefirst user. The first user may review the notification, which isdisplayed on the display screen of the first computing device. The firstuser may generate and execute instructions on the first computing deviceto close the digital ticket on verifying that the farm task is completedby the second user.

The updates to the digital ticket may be used for electronicrecordkeeping. For example, in the embodiments where the farm machineryis a diesel pump, a computer (e.g., the first computer, the secondcomputer, or the server) may generating a digital log of dieselconsumption. An illustrative digital log for diesel consumption is shownin FIG. 7B.

An illustrative mobile application may further provide a map view mode.A user may select a map view mode at a navigation menu at the bottom ofan interface of the mobile application. Based upon such selection, themobile application may display the captured data for a workspace and thegeolocations of members associated with the workspace on a map. Themobile application may dynamically update the map as new data iscaptured at various locations by the members.

The mobile application may further enable electronic transactions. Forexample, the mobile application may generate transmit a stock-takedigital ticket associated with a stock re-order to a predefined set ofsuppliers. As another example, the mobile application may generate aget-a-quote digital ticket. The user may send the get-a-quote digitalticket for a purchase as a part of a transaction within the mobileapplication. To complete the transaction within the mobile application,the mobile application may update the get-a-quote digital ticket withthe corresponding invoice and payment.

The mobile application may also provide a workflow management platform.A back-end system associated with the mobile application may structurerecorded data according to a workflow defined by the user, where thedifferent tickets combine together to form the workflow. The mobileapplication may access the data according to different steps of theworkflow and may generate different digital tickets within the workflow.

Although certain non-limiting embodiments have been presented, variouschanges, substitutions, permutations, and alterations may be madewithout departing from the scope of the appended claims. Further, thesteps of the methods described herein may be carried out in any suitableorder, or simultaneously where appropriate. Thus, the scope of thedisclosure should not necessarily be limited by this description.

Unless specifically stated otherwise as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing,” “computing,”“transmitting,” “receiving,” “determining,” “displaying,” “identifying,”“presenting,” “establishing,” or the like, may refer to the action andprocesses of a data processing system, or similar electronic device thatmanipulates and transforms data represented as physical (electronic)quantities within the system's registers and memories into other datasimilarly represented as physical quantities within the system'smemories or registers or other such information storage, transmission ordisplay devices. The system or portions thereof may be installed on anelectronic device.

The embodiments may relate to an apparatus for performing one or more ofthe functions described herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise a specialpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina machine (e.g., computer) readable storage medium, such as, but is notlimited to, any type of disk including floppy disks, optical disks,CD-ROMs and magnetic-optical disks, read only memories (ROMs), randomaccess memories (RAMs) erasable programmable ROMs (EPROMs), electricallyerasable programmable ROMs (EEPROMs), magnetic or optical cards, or anytype of media suitable for storing electronic instructions foroperations on a processor, and each coupled to a bus.

The embodiments described herein are described as software executed onat least one server, though it is understood that embodiments may beconfigured in other ways and retain functionality. The embodiments maybe implemented on known devices such as a personal computer, a specialpurpose computer, cellular telephone, personal digital assistant(“PDA”), a digital camera, a digital tablet, an electronic gamingsystem, a programmed microprocessor or microcontroller and peripheralintegrated circuit element(s), and ASIC or other integrated circuit, adigital signal processor, a hard-wired electronic or logic circuit suchas a discrete element circuit, a programmable logic device. In general,any device capable of implementing the processes described herein may beused to implement the systems and techniques according to thisdisclosure.

The embodiments may relate to an apparatus for performing one or more ofthe functions described herein. This apparatus may be speciallyconstructed for the required purposes or be selectively activated orreconfigured by computer executable instructions stored innon-transitory computer memory medium or non-transitorycomputer-readable storage medium.

It is to be appreciated that the various components of the technologymay be located at distant portions of a distributed network or theInternet, or within a dedicated secured, unsecured, addressed/encoded orencrypted system. Thus, it should be appreciated that the components ofthe system may be combined into one or more devices or co-located on aparticular node of a distributed network, such as a telecommunicationsnetwork. As will be appreciated from the description, and for reasons ofcomputational efficiency, the components of the system may be arrangedat any location within a distributed network without affecting theoperation of the system. Moreover, the components could be embedded in adedicated machine.

Furthermore, it should be appreciated that the various links connectingthe elements may be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying or communicating data to and from the connected elements. Theterm “module” as used herein may refer to any known or later developedhardware, software, firmware, or combination thereof that is capable ofperforming the functionality associated with that element.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the subject matter (especially in the context ofthe following claims) are to be construed to cover both the singular andthe plural, unless otherwise indicated herein or clearly contradicted bycontext. The terms “comprising,” “having,” “including,” and “containing”are to be construed as open-ended terms (i.e., meaning “including, butnot limited to,”) unless otherwise noted. Recitation of ranges of valuesherein are merely intended to serve as a shorthand method of referringindividually to each separate value falling within the range, unlessotherwise indicated herein, and each separate value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein may be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof all examples, or language (e.g., “such as”) provided herein, isintended merely to better illuminate the disclosure and does not pose alimitation on the scope of the disclosure unless otherwise claimed. Nolanguage in the specification should be construed as indicating anynon-claimed element as essential to the practice of the disclosure.

Presently preferred embodiments of this disclosure are described herein,including the best mode known to the inventors for carrying out thedisclosure. Variations of those preferred embodiments may becomeapparent to those of ordinary skill in the art upon reading theforegoing description. The inventors expect skilled artisans to employsuch variations as appropriate, and the inventors intend for thedisclosure to be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein orotherwise clearly contradicted by context.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation may becombined with one or more features of any other implementation.

What is claimed is:
 1. A computer-implemented method comprising:generating, by a first instance of an application in a first computer, adigital board associated with a farm project within a workspaceassociated with a first type of farm operation; generating, by the firstinstance of the application in the first computer, a digital ticketwithin the digital board, the digital ticket configured for a farm taskassociated with the farm project, and the digital ticket including adata template configured to receive data records associated with thefarm task; transmitting, by the first instance of the application in thefirst computer, the digital ticket to a second instance of theapplication in a second computer; receiving, by a second instance of theapplication in a second computer, the digital ticket transmitted by thefirst instance of the application in the first computer; in response tothe second instance of the application in the second computer receivingan indication to activate the digital ticket; continuously tracking, bythe second instance of the application in the second computer,geolocation of the second computer; continuously retrieving, by thesecond instance of the application in the second computer, dispensingdata through an application programming interface of a farm machineryassociated with the farm task; continuously updating, by the secondinstance of the application in the second computer, the digital ticketbased on the continuously tracked geolocation and continuously retrieveddispensing data; determining, by the second instance of the applicationin the second computer, whether the farm task is completed based uponcontinuous updates to the digital ticket; and transmitting, by thesecond instance of the application in the second computer to the firstinstance of the application in the first computer, a final updateddigital ticket and a notification that the farm task is completed. 2.The computer-implemented method of claim 1, further comprisingdisplaying, by the first computer, the final updated digital ticket onan interactive graphical user interface of the first computer.
 3. Thecomputer-implemented method of claim 2, further comprising parsing, bythe first computer, information associated with the final updateddigital ticket displayed on the interactive graphical user interface toanalyze parsed information and verify that the farm task is competed. 4.The computer-implemented method of claim 3, further comprisingexecuting, by the first computer, one or more instructions to closefinal updated digital ticket.
 5. The computer-implemented method ofclaim 1, further comprising transmitting, by the first computer, thenotification to a phone number of a first user operating the firstcomputer.
 6. The computer-implemented method of claim 5, furthercomprising executing, by the first computer, one or more instructions toclose the final updated digital ticket when the first user requests toclose the final updated digital ticket.
 7. The computer-implementedmethod of claim 1, wherein the farm machinery may comprise one or moremachines to execute the farm task.
 8. The computer-implemented method ofclaim 7, wherein each machine comprises a dispensing application, andwherein the dispensing application is a computer software program. 9.The computer-implemented method of claim 8, wherein the dispensingapplication is linked to the application of the first computer and thesecond computer.
 10. The computer-implemented method of claim 1, whereinthe first instance of the application is a mobile version of theapplication installed on the first computer, and wherein the secondinstance of the application is the mobile version of the applicationinstalled on the second computer.
 11. A system comprising: a firstcomputer having a first application of an application, wherein a firstinstance of the application in the first computer is configured to:generate a digital board associated with a farm project within aworkspace associated with a first type of farm operation; generate adigital ticket within the digital board, the digital ticket configuredfor a farm task associated with the farm project, and the digital ticketincluding a data template configured to receive data records associatedwith the farm task; transmit the digital ticket to a second instance ofthe application in a second computer, wherein the second instance of theapplication in the second computer is configured to: receive a secondinstance of the application in a second computer, the digital tickettransmitted by the first instance of the application in the firstcomputer; in response to the second instance of the application in thesecond computer receiving an indication to activate the digital ticket;continuously track geolocation of the second computer; continuouslyretrieve dispensing data through an application programming interface ofa farm machinery associated with the farm task; continuously update thedigital ticket based on the continuously tracked geolocation andcontinuously retrieved dispensing data; determine that the farm task iscomplete based upon continuous updates to the digital ticket; andtransmit to the first instance of the application in the first computer,a final updated digital ticket and a notification that the farm task iscomplete.
 12. The system of claim 11, wherein the first computer isfurther configured to display the final updated digital ticket on aninteractive graphical user interface of the first computer.
 13. Thesystem of claim 12, wherein the first computer is further configured toparse information associated with the final updated digital ticketdisplayed on the interactive graphical user interface to analyze parsedinformation and verify that the farm task is competed.
 14. The system ofclaim 13, wherein the first computer is further configured to executeone or more instructions to close final updated digital ticket.
 15. Thesystem of claim 11, wherein the first computer is further configured totransmit the notification to a phone number of a first user operatingthe first computer.
 16. The system of claim 15, wherein the firstcomputer is further configured to execute one or more instructions toclose the final updated digital ticket when the first user requests toclose the final updated digital ticket.
 17. The system of claim 11,wherein the farm machinery may comprise one or more machines to executethe farm task.
 18. The system of claim 17, wherein each machinecomprises a dispensing application, and wherein the dispensingapplication is a computer software program.
 19. The system of claim 18,wherein the dispensing application is linked to the application of thefirst computer and the second computer.
 20. The system of claim 11,wherein the first instance of the application is a mobile version of theapplication installed on the first computer, and wherein the secondinstance of the application is the mobile version of the applicationinstalled on the second computer.